Statements of what success looks like for this project:

1. Having the data sets organized with links on one page. Having access to the data would be great.
2. A way to access database data directly from multiple platforms avoiding 'out-of-sync' issues.
3. Creation of a Matlab toolbox for loading, analyzing, and visualizing Climate Forecast formatted data accessible from OPeNDAP servers.
4. Consistent interface to data so that applications may be easily built.
5. Geared toward science use. Need to match access interface to tools that people use.
6. Stated in the form of a Use Case: Able to construct a climatology from ROV, AUV, BOG, and Mooring CTD data without too much fuss.
7. Be able to go to a single server and find a tree of data where each leaf or branch has a standard way of accessing the data.
   • This is programmatic access where libraries are available to developer to build applications to access all the data
   • Preference for Unidata's Common Data Model and THREDDS servers
8. It's be nice to have data browse capability along with programmatic access.
9. Being on a warm beach with a cold beer in hand.

Notes for 14 Jan 2009 meeting

Attending: Mike McCann, Fred Bahr, Kevin Gomes, Brian Schlining, Reiko Michisaki, Mike Godin, Francisco Chavez, John Ryan

• Review of above statements

John will get back to me with his use cases. Submitted by email

• Review of Work Breakdown Structure

Moved Brian's 40 hours to the R2 release target making the "Develop Matlab toolkit for using THREDDS accessible data" item task 120 hours for delivery by R2: 31 July 2009.

Need for a Systems Engineering Diagram identifying data sets, their hosts, servers, services and those reponsible stated. Francisco and Reiko will work on this and post it in this space.

• Meeting schedule (weekly, monthly, never?) 

Monthly, about in the middle of the month. Mike will make announcements